Starting a batch of Service Containers

This topic describes the process of initializing a set of Service Containers in batches.

On machines with limited CPU capacity, it has been observed that when there are many Service Containers, the OpenText Process Suite Platform (<instance name>) could not start all of them at once. This is because simultaneous start of all these Service Containers results in insufficient CPU share among the VMs. This in turn causes errors or time outs during the startup.

To resolve this, a set of Service Containers are started in batches, so that the CPU utilization is spread over a period of time. This enables a fair share of CPU cycles for all Service Containers. Refer to Administrator's role in the process of starting a set of processors for information on configuration requirements.
This solution is applicable only in the following circumstances

• During the startup of the OpenText Process Suite Platform (<instance name>) and not after it has started.
  
• For automatic start, enabled for Service Containers.
  
  The following steps indicate the functionality of starting a set of Service Containers in batches.
  
  

1. At the startup, Monitor reads all the Service Containers that are configured on its machine.
   
2. It then reads each of the application connector's configurations and retrieves the dependency list.
   Note: Dependency list refers to a set of name spaces on which the application is dependent upon at the start up ( namespaces used to invoke any Web service in the open () Web service operation of the Application connector). The dependency list is associated with the application connector, hence must be a part of the Application Connector configuration. Incase of no dependency list, Monitor treats it to be 'no dependency to start the Service Container' which implies that such a Service Container would be in the initial batches. The dependency list must not contain namespaces of LDAP and Monitor.
   
3. Monitor consolidates all these dependency lists and sorts the Service Containers accordingly.
   Note: The pre-defined batch size is used to determine the number of Service Containers that are to be started simultaneously.
   
4. A Service Container is initialized by invoking its Application connector's open()Web service operation. After this Web service operation is invoked successfully, the client VM communicates to the Monitor that the initialization is complete. The timeout defined at the monitor would govern the maximum time for this entire operation.
   
5. After the timeout expiry or successful initialization of the Service Container the Monitor picks up the next Service Container from the sorted list .
   
   A set of Service Containers are initialized in batches.